Random Access

     This stuff is totally unsupported. These are various excerpts from posts, text files, other magazines, etc. that I have found in my travels. I have tried to at least give the author credit, but the magazine or text file it originally appeared in is not always easy to find out. (These are unedited for the most part so my apologies for lack of spellng, grammar, etc)

 
How to get your neighbor's phone number:

Do you have a neighbor who really pisses you off? Well follow these simple steps and you be screwing with them in no time.

Bring a phone and find your victim's little telephone box. Probably it's stasted behind some thorn bushes or in some equally annoying place. Open up the box and put the phone cord in the modular jack.  Then dial 830. The phone should ring and an operator's voice will say the phone number.  

Now call them up. They'll probably wet their pants when they find out you have their number. 

I know that this works in all of Southwestern Bell.  But as for other phone companies, I'm not sure.

NORTHwest ATTACKer

 
Another way to hack On Guard:
   
     Go to Find File and search for Guard. One of the search results will be the On Guard control panel, double-click it. You should get a screen saying, please enter admin password...press cancel. That should take you back to the finder, now do shit in the Finder, you can do pretty much anything, EXCEPT open stuff in the System Folder. You can drag stuff out from the system folder, open it, or trash it, but you can't do it directly. (By the way, to get back to "normal" user privileges, just restart the computer) So to get rid of that, go to the Extensions Manager and drag it out into the finder, then double click it. Then change the extensions making sure to TURN OFF any On Guard related ones. Put the Extensions Manager back into the control panels folder and restart the computer, now the computer is TOTALLY unprotected.

     NOTE: The sysop can check the computer you're on and see if On Guard is running. (It's a feature in the software) All he has to do is ping the computer, and it'll tell him whether On Guard is on or not.  If the computer is shut down though, if he pings it, it will not respond.  SO, if the sysop of the network On Guard is running pings a computer which he sees you are currently using and it does not respond, that means one of two things, you are using a computer that is shut down (SURE....) OR On Guard was disabled, probably by you. So the moral of the story is, DO NOT turn off On Guard when the sysop is around. Have fun folks.

NAßSTER

 
Easy Passworded Web Pages. (Not corporate or federal)

These things are really funny!

The functions:
If you are accessing a page that uses a password protection of this kind, you will get a Dialogbox that tells you some thing and then it looks a little like this:

Name:

Password:

Hmmmm, so we think, this thing can not be only SERVER oriented (which means that the whole data is first sent over the Internet and then executed on your PC, and then deleted again), no there has to be something on your computer already so this little sucker can pop up that goddamn fast!

Most times these protections are written in JAVA, or PERL or some pseudo stuph like this. :-) So, if you know a little where to look you will easily find the file (Cache of course) which has the Form commands in it.
If you dont follow these steps:

- Go to your System Folder

- Go to your Preferences

- go to your Netscape/Cache folder

- look for all the HTML files in it and look through them (a little tip, clear your whole cache then access the site with the password and you dont have to look through 300+ html files)

Now that you found the password thingy, the script should look a little like the following thing:

some lines should show up the following command:

INPUT TYPE=password NAME="Password:"

Ok, thats where the form part of the password box is created, but how does the damn server know that we entered the correct password? Thats pretty easy, its called an "array"!  The client PC (your little Mac, sorry but I am sitting on a brand new SGI) :-) sends the two data packets back in ONE packet. Hmmmm, so whats the IDEA? Its easier than you might think! We have to prevent the server from recognizing the packet as a secured password packet! So how do we do that?

Did you ever site in your room listening to PRODOGY at about 120 db and reading your homework? You actually can read the book but you dont get the information outta it because the music is TOO loud!
Well, the same thing happens to a server if he gets a whole crapload of data and has to filter the important stuff out of it! So, what we do is downloading a little program called "Ping of Death" or something like it and get a FAST connection. (a Dual T1 should be alright) and enter for the packet size a huge number like:

650000 (thats HUGE)

then for the packet number a huge number:

not under 500!

then we enter the IP adress of the damn server and start pinging.

Now open your browser and go to the site (you will recongnize it takes forever to connect!)
then there will be the stupid Password Window, :

NOW ENTER A LONG NAME AND A LONG PASSWORD!!!! (Because those get encrypted and even longer)

Now it will maybe take a fucking long time, or you will get the Authorisation screen again! Try it until it takes veeeery long....

When the server times out, you should be in!

Matrix

 
How to Cover Your Tracks On Unix.

I've done this on my last shell account and it worked awesome. I typed cat /etc/passwd and logged the telnet session so I would have all the passwords logged in text. Type ls -la in your home dir and you will see a bunch of files that start with a period like .bash_history. The file .bash_history is a log of what you have done in your telnet sessions.  Type pico .bash_history to take a look at it. To delete it make sure you sign off then come back on cause the log is not sent to the file untill you signoff so sign back on and type rm .bash_history to delete it. The only thing it will log is the rm .bash_history but at least they dont know what you have done during your telnet sessions.         

HagZ